Octopus Deploy Mcp Server

Created By
Arman Nourifar10 months ago
A Model Context Protocol (MCP) server for interacting with Octopus Deploy. This server provides tools for managing projects, releases, and deployments through the MCP protocol. Features Project Management: List and query Octopus Deploy projects Release Management: Get latest releases and create new releases Deployment Management: Deploy releases and check deployment status Multi-Space Support: Work with different Octopus Deploy spaces Docker Support: Containerized deployment for easy integration
Overview

what is Octopus Deploy MCP Server?

Octopus Deploy MCP Server is a Model Context Protocol (MCP) server designed for interacting with Octopus Deploy, providing tools for managing projects, releases, and deployments through the MCP protocol.

how to use Octopus Deploy MCP Server?

To use the server, clone the repository, build the Docker image, and configure your MCP client with the necessary Octopus Deploy API key and server URL.

key features of Octopus Deploy MCP Server?

  • Project Management: List and query Octopus Deploy projects
  • Release Management: Get latest releases and create new releases
  • Deployment Management: Deploy releases and check deployment status
  • Multi-Space Support: Work with different Octopus Deploy spaces
  • Docker Support: Containerized deployment for easy integration

use cases of Octopus Deploy MCP Server?

  1. Managing multiple projects in Octopus Deploy
  2. Automating release creation and deployment processes
  3. Integrating with CI/CD pipelines for seamless deployments

FAQ from Octopus Deploy MCP Server?

  • What is required to run the Octopus Deploy MCP Server?

You need Docker, a valid Octopus Deploy server URL, and an API key with appropriate permissions.

  • How do I troubleshoot common issues?

Check the server logs for detailed error information and ensure your API key and server URL are correct.

  • Can I run this server without Docker?

Yes, you can set up the server locally without Docker by following the local setup instructions.

Server Config

{
  "mcpServers": {
    "octopus-deploy-mcp-server": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "OCTOPUS_URL",
        "-e",
        "OCTOPUS_API_KEY",
        "octopus-deploy-mcp:latest",
        "octopus-deploy-mcp"
      ],
      "env": {
        "OCTOPUS_URL": "https://your-octopus-server.com",
        "OCTOPUS_API_KEY": "${input:octopus-api-key}"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
Arman Nourifar
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

8 hours ago
Alloy

2 days ago